Image with audio conversation system and method

ABSTRACT

A system and method are presented to allow audio communication between users concerning an image. The originator of the communication uses a mobile device app to select an image and record an audio commentary. The image and commentary are encoded together into a video file. The app uses a server to analyze the recipient address to determine the preferred mode of delivery. If the recipient is a known user of the app, the file is delivered through a proprietary communication system and viewed by the recipient using the app. Otherwise, the originator&#39;s app delivers the file through MMS or e-mail for the recipient to view using a standard video player. E-mail and MMS communications include a link for the recipient to download the app. The recipient can download the app and register as a user, which causes a server to download previously delivered files to the new user&#39;s app.

CROSS REFERENCE TO RELATED APPLICATION

This application is related to the content found in U.S. patent application Ser. Nos. 13/832,177; 13/832,744; 13/834,347; all filed on Mar. 15, 2013, and U.S. patent application Ser. No. 13/947,016, filed on Jul. 19, 2013, all of which are hereby incorporated by reference.

FIELD OF THE INVENTION

The present application relates to the field of image-centered communication between users. More particularly, the described embodiments relate to a system and method for bi-directional audio communication centered on a visual image element.

SUMMARY

One embodiment of the present invention provides audio communication between users concerning an image. The originator of the communication uses an app operating on a mobile device to create or select a photograph or other image. The same app is then used to attach an audio commentary to the image. The app encodes the audio commentary and the image together into a video file that can be viewed by video players included with modern mobile devices. This video file is one example of an “audio image” file used by the present invention.

The originator can then select one or more recipients to receive the video file. Recipients are identified by e-mail addresses, cell phone numbers, or user identifiers used by a proprietary communication system. The app analyzes each recipient address to determine the preferred mode of delivery for the video file. If the recipient also uses the app, the file is delivered through the proprietary communication system and received by the app on the recipient's mobile device. Otherwise, the file is delivered through MMS (if the recipient is identified by a telephone number) or through e-mail (if the recipient is identified by an e-mail address). Regardless of how the file is sent, a message containing the file and the particulars of the transmission are sent to the server managing the proprietary communication system.

When the file is sent through MMS or e-mail, it is accompanied by a link that allows the recipient to download an app to their mobile device to continue the dialog with the originator. When the link is followed, the user can download the app. Part of the set-up process for the app requires that new users identify their e-mail address and cell phone. This set-up information is communicated to the proprietary server, which can then identify audio image messages that were previously sent to the recipient through either e-mail or MMS message. Those audio image messages are then presented through an in-box in the app, where they can be selected for downloading and presentation to the newly enrolled user.

All recipients of the audio image file can play the file in order to view the image and hear the originator's audio commentary. Recipients using the app on their mobile devices can record a reply audio commentary. This reply audio is then encoded by the app into a new video file, where the reply audio is added to the beginning of the previous audio track and the video track remains a static presentation of the originally selected image. This new video file can be returned to the originator, allowing the originator to create a new response to the reply audio.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of a system utilizing the present invention.

FIG. 2 is a schematic diagram showing a database accessed by a server used in the system of FIG. 1.

FIG. 3 is a schematic diagram showing the components of an audio image file.

FIG. 4 is a schematic diagram showing the components of a new audio image file after an audio comment is added to the audio image file of FIG. 3.

FIG. 5 is a plan view of a mobile device displaying a user interface provided by an app.

FIG. 6 is a plan view of the mobile device of FIG. 5 displaying a second user interface provided by the app.

FIG. 7 is a flow chart showing a method of creating, transmitting, and responding to an audio image file.

FIG. 8 is a flow chart showing the detailed steps of responding to an audio image file.

FIG. 9 is a flow chart showing the method of receiving an audio image file without the initial use of an app.

DETAILED DESCRIPTION System 100

FIG. 1 shows a system 100 in which a mobile device 110 can create and transmit audio image files to other users. Audio image files allow users to have a bi-directional, queued, audio communication about a particular visual image. The mobile device 110 can communicate over a wide area data network 150 with a plurality of computing devices. In FIG. 1, the mobile device 110 communicates over network 150 with an audio image server 160 to send an audio image to mobile device 168, and communicates over the same network 150 with an e-mail server 170 in order to send an e-mail containing an audio image to a second mobile device 174. In one embodiment, the wide area data network is the Internet. The mobile device 110 is also able to communicate with an multimedia messaging service center (“MMS center”) 180 over MMS network 152 in order to send an audio image within an MMS message to a third mobile device 184.

The mobile device 110 can take the form of a smart phone or tablet computer. As such, the device 110 will include a microphone 112 and a camera 114 for receiving audio and visual inputs. The device 110 also includes a touch screen user interface 116. In the preferred embodiment, touch screen 116 both presents visual information to the user over the display portion of the touch screen and also receives touch input from the user.

The mobile device 110 communicates over the data network 150 through a data network interface 118. In one embodiment, the data network interface 118 connects the device 110 to a local wireless network that provides connection to the wide area data network 150. The data network interface 118 preferably connects via one of the Institute of Electrical and Electronics Engineers' (IEEE) 802.11 standards. In one embodiment, the local network is based on TCP/IP, and the data network interface 118 includes a TCP/IP protocol stack.

Similarly, the mobile device 110 communicates over the MMS network 152 via a cellular network interface 120. In the preferred embodiment, the mobile device 110 sends multi-media messaging service (“MMS”) messages via the standards provided by a cellular network 152, meaning that the MMS network 152 used for data messages is the same network 152 that is used by the mobile device 110 to make cellular voice calls. In some embodiments, the provider of the cellular data network also provides an interface to the wide area data network 150, meaning that the MMS or cellular network 152 could be utilized to send e-mail and proprietary messages as well as MMS messages. This means that the actual physical network interface 118, 120 used by the mobile device 110 is relatively unimportant. Consequently, the following description will focus on three types of messaging: e-mail, MMS, and proprietary messaging, without necessarily limiting these messages to a particular network 150, 152 or network interface 118, 120. The use of particular interfaces 118, 120 and networks 150, 152 in this description is merely exemplary.

The mobile device 110 also includes a processor 122 and a memory 130. The processor 120 can be a general purpose CPU, such as those provided by Intel Corporation (Mountain View, Calif.) or Advanced Micro Devices, Inc. (Sunnyvale, Calif.), or a mobile specific processor, such as those designed by ARM Holdings (Cambridge, UK). Mobile devices such as device 110 generally use specific operating systems 140 designed for such devices, such as iOS from Apple Inc. (Cupertino, Calif.) or ANDROID OS from Google Inc. (Menlo Park, Calif.). The operating system 140 is stored on memory 130 and is used by the processor 120 to provide a user interface for the touch screen display 116, handle communications for the device 110, and to manage and provide services to applications (or apps) that are stored in the memory 130. In particular, the mobile device 100 is shown with an audio image app 132, MMS app 142, and an e-mail app 144. The MMS app 142 is responsible for sending, receiving, and managing MMS messages over the MMS network 152. Incoming messages are received from the MMS center 180, which temporarily stores incoming messages until the mobile device 110 is able to receive them. Similarly, the e-mail app 144 sends, receives, and manages e-mail messages with the aid of one or more e-mail servers.

The audio image app 132 is responsible for the creation of audio image files, the management of multiple audio image files, and the sending and receiving of audio image files. In one embodiment, the audio image app 132 contains programming instructions 134 for the processor 122 as well as audio image data 136. The image data 136 will include all of the undeleted audio image files that were created and received by the audio image app 132. In the preferred embodiment, the user is able to delete old audio image files that are no longer desired in order to save space in memory 130.

The app programming 134 instructs the processor 122 how to create audio image files. The first step in so doing is either the creation of a new image file using camera 114, or the selection of an existing image file 146 accessible by the mobile device 110. The existing image file 146 may be retrieved from the memory 130 of the mobile device 110, or from a remote data storage service (not shown in FIG. 1) accessible over data network 150. The processor 122 then uses the display 116 to show the image to the user, and allows the user to input an audio commentary using the microphone 112. The app programming 134 instructs the processor 122 how to combine the recorded audio data with the image into a combined video file. In the preferred embodiment, the app programming 134 takes advantage of the ability to link to existing routines in the operating system 140 in order to render the video file. In most cases, these tools take the form of a software development kit (or “SDK”) or access to an application programming interface (or “API”). For example, Apple's iOS gives third-party apps access to an SDK to render videos using the H.264 video codec.

After the app programming 134 causes the processor 122 to create the video file (also known as the audio image file), the app programming 134 causes the processor 122 to present a user input screen on display 116 that allows the user to select a recipient of the audio image file. In one embodiment, the user is allowed to select recipients from existing contact records 148 that already exist on the mobile device 110. These same contact records may be used by the MMS app 142 to send MMS messages and the E-mail app 144 to send e-mail messages. In one embodiment, when the user selects a contact as a recipient, the app programming 134 identifies either an e-mail address or a cell phone number for the recipient.

Once the recipient is identified, the app 132 determines whether the audio image file should be sent to the recipient using the audio image server 160 and its proprietary communications channel, or should be sent via e-mail or MMS message. This determination is based on whether or not the recipient mobile device is utilizing the audio image app 132. A mobile device is considered to be using the audio image app 132 if the app 132 is installed on the device and the user has registered themselves as a user of the app 132 with the audio image server 160. In FIG. 1, mobile device 168 is using the audio image app 132, while mobile devices 174 and 184 are not using the app 132.

To make this determination, the app programming 134 instructs the processor 122 to send a user verification request containing the e-mail address or cell phone of the recipient (both of which could be considered the recipient's “audio image address”) to the audio image server 160. The server 160 is a programmed computing device operating a processor 161 under control of server programming 163 that is stored on the memory 162 of the audio image server 160. The processor 161 is preferably a general purpose CPU of the type provided by Intel Corporation or Advanced Micro Devices, Inc., operating under the control of a general purpose operating system such as Mac OS by Apple, Inc., Windows by Microsoft Corporation (Redmund, Wash.), or Linux (available from a variety of sources under open source licensing restrictions). The server 160 is in further communication with a database 164 that contains information on user customers, the audio image addresses of the customers, and audio image files. The server 160 responds to the user verification request by consulting the database 164 to determine whether each recipient's audio image address is associated in the database 164 with a known user of the app 132. The server 160 then informs the mobile device 110 of its findings.

Although the server 160 is described above as a single computer with a single processor 161, it would be straight-forward to implement server 160 as a plurality of separate physical computers operating under common or cooperative programming. Consequently, the terms server, server computer, or server computers should all be viewed as covering situations utilizing one or more than one physical computer.

If the server 160 indicates that the recipient device 168 is associated with a known user of the app 132, then the audio image file 166 is transmitted to that mobile device 168 via the server 160. In effect, the mobile device 110 transmits the audio image file 166 along with metadata that identifies the sender and recipient of the file 166. The server 160 stores this information in database 164, and informs the recipient mobile device 168 that it has received an audio image file 166. If the device 168 is powered on and connected to the data network 150, the audio image file 166 can be immediately transmitted to the mobile device 168, where it is received and managed by the audio image app 132 on that device 168. The audio image app 132 would then inform its user that the audio image file is available for viewing. In the preferred embodiment, the app 132 would list all received audio image files in a queue for selection by the user. When one of the files is selected, the app 132 would present the image and play the most recently added audio commentary made about that image. The app 132 would also give the user of device 168 the ability to record a reply commentary to the image, and then send that reply back to mobile device 110 in the form of a new audio image file. The new audio image file containing the reply comment could also be forwarded to third parties.

If the server 160 indicates that the recipient device 174 or 184 is not associated with a user of the audio image app 132, the mobile device 110 will send the audio image file without using the proprietary communication system provided by the audio image server 160. If the audio image address is an e-mail address, the audio image app 132 on device 110 will create an e-mail message 172 to that address. This e-mail message 172 will contain the audio image file as an attachment, and will be sent to an e-mail server 170 that receives e-mail for the e-mail address used by device 174. This server 170 would then communicate to the device 174 that an e-mail has been received. If the device 174 is powered on and connected to the data network 150, an e-mail app 176 on the mobile device 174 will receive and handle the audio image file within the received e-mail message 172.

Similarly, if the audio image address is a cell phone number, the audio image app 132 will create an MMS message 182 for transmission through the cellular network interface 120. This MMS message 182 will include the audio image file, and will be delivered to an MMS center 180 that receives MMS messages for mobile device 184. If the mobile device 184 is powered on and connected to the MMS network 152, an MMS app 186 on mobile device 184 will download and manage the MMS message 182 containing the audio image file 182. Because the audio image file in either the e-mail message 172 and the MMS message 182 is a standard video file, both mobile devices 174 and 184 can play the file using standard programming that already exists on the devices 174, 184. This will allow the devices 174, 184 to display the image and play the audio commentary concerning the image as input by the user of device 110 without requiring the presence of the audio image app 132. However, without the presence of the app 132, it would not be possible for either device 174, 184 to easily compose a reply audio image message that could be sent back to device 110.

In the preferred embodiment, the e-mail message 172 and the MMS message 182 both contain links to location 190 where the recipient mobile devices 174, 184 can access and download the audio image app 132. The message will also communicate that downloading the app 132 at the link will allow the recipient to create and return an audio reply to this audio image file. The linked-to download location 190 may be an “app store”, such as Apple's App Store for iOS devices or Google's Play Store for Android devices. The user of either device 174, 184 can use the provided link to easily download the audio image app 132 from the app store 190. When the downloaded app 132 is initially opened, the user is given the opportunity to register themselves as a user by providing their name, e-mail address(es) and cell phone number(s) to the app 132. The app 132 then shares this information with the audio image server 160, which creates a new user record in database 164. The server 160 can then identify audio image messages that were previously sent to that user and forward those messages to the user. At this point, the user can review the audio image files using the app 132, and now has the ability to create and send a reply audio message as a new audio image file.

In some embodiments, the audio image file is delivered as a video file to e-mail recipients and MMS recipients, but is delivered as separate data elements to mobile devices 168 that utilize the audio image app 132. In other words, a single video file is delivered via an e-mail or MMS attachment, while separate data elements are delivered to the mobile devices 168 that use the audio image app 132. In these cases, the “audio image file” delivered to the mobile device 168 would include an image file compressed using a still-image codec (such as JPG, PNG, or GIF), one or more audio files compressed using an audio codec (such as MP3 or AAC), and metadata identifying the creator, creation time, and duration of each of the audio files. The audio image app 132 would then be responsible for presenting these separate data elements as a unified whole.

In sending the MMS message 182, the mobile device 130 may take advantage of the capabilities of the separate MMS app 144 residing on the mobile device 110. Such capabilities could be accessed through an API or SDK provided by the app 144. Alternatively, the audio image app programming 134 could contain all of the programming necessary to send the MMS message 182 without requiring the presence of a dedicated MMS app 142. Similarly, the mobile device 130 could use the capabilities of a separate e-mail app 144 to handle the transmission of the e-mail message 172 to mobile device 174, or could incorporate the necessary SMTP programming into the programming 134 of the audio image app 132 itself.

Database 164

FIG. 2 shows one embodiment of database 164 that is used to track users and audio image messages. The database 164 may be stored in the memory 162 of the audio image server 160, or it may be stored in external memory accessible to the server 160 through a bus or network 165. The database 164 is preferably organized as structured data, such as separate tables in a relational database or as database objects in an object-oriented database environment. Database programming 163 stored on the memory 162 of the audio image server 160 directs the processor 161 to access, manipulate, update, and report on the data in the database 164. FIG. 2 shows the database 164 with tables or objects for audio image messages 200, audio image data or files 210, users 220, e-mail addresses 230, cell phone numbers 240, and audio image user IDs 250. Since e-mail addresses 230, cell phone numbers 240, and audio image user IDs 250 can all be used as a recipient or sender address for an audio image message 200, FIG. 2 shows a dotted box 260 around these database entities 230, 240, 250 so that this description can refer to any of these address types as an audio image address 260. These addresses 260 can all be considered electronic delivery addresses, as the addresses 260 each can be used to deliver an electronic communication to a destination.

Relationships between the database entities are represented in FIG. 2 using crow's foot notation. For example, FIG. 2 shows that each user database entity 220 can be associated with a plurality of e-mail address 230 and cell phone numbers 240, but with only a single audio image user ID 250. Meanwhile, each e-mail address 230, cell phone number 240, and audio image user ID 250 (i.e., each audio image address 260) is associated with only a single user entity 220. Similarly, each audio image message 200 can be associated with a plurality of audio image addresses 260 (e-mail addresses 230, cell phone numbers 240, and audio image user IDs 250), which implies that a single message 200 can have multiple recipients. In the preferred embodiment, the audio image message 200 is also associated with a single audio image address 260 to indicate the sender of the audio image message 200. The fact that each audio image address 260 can be associated with multiple audio image messages 200 indicates that a single audio image address 260 can be the recipient or sender for multiple messages 200. FIG. 2 also shows that each audio image message database entity 200 is associated directly with an audio image file 210. This audio image file 210 can be a single video file created by the audio image app 132, or can be separate image and audio files along with metadata describing these files. The distinctions between these database entities 200-250 are exemplary and do not need to be maintained to implement the present invention. For example, it would be possible for the audio image message 200 to incorporate the audio image data or file 210 in a single database entity. Similarly, each of the audio image addresses 260 could be structured as part of the user database entity 220. The separate entities shown in FIG. 2 are presented to assist in understanding the data that is maintained in database 164 and the relationships between that data.

Associations or relationships between the database entities shown in FIG. 2 can be implemented through a variety of known database techniques, such as through the use of foreign key fields and associative tables in a relational database model. In FIG. 2, associations are shown directly between two database entities, but entities can also be associated through a third database entity. For example, a user database entity 200 is directly associated with one or more audio image addresses 260, and through that relationship the user entity 200 is also associated with audio image messages 200. These relationships can also be used to indicate different roles. For instance, an audio image message 200 may be related to two different audio image user IDs 250, one in the role of a recipient and one in the role as the sender.

Audio Image File 300

An example audio image file 300 is shown in FIG. 3. In this example, the audio image file 300 is a video file containing a video track 310, an audio track 320, and metadata 330. The video track contains a single, unchanging still image 312 that is compressed using a known video codec. When the H.264 codec is used, for example, the applicable compression algorithms will ensure that the size of the video track 310 will not increase proportionally with the length of the audio track, as an unchanging video track is greatly compressed using this codec. While the H.264 codec does use keyframes that contain the complete video image, intermediate frames contain data only related to changes in the video signal. With an unchanging video feed, the intermediate frames do not need to reflect any changes. By increasing the time between keyframes, even greater compression of the video track 310 is possible.

In the audio image file 300 shown in FIG. 3, the audio track contains two separate audio comments 322, 324. In FIG. 3, the first comment 322 to appear in the track 320 is actually the second to be recorded chronologically. This means that the audio track 320 of the audio image file 300 will start with the most recent comment 322. When a standard video player plays this audio image file 300, the most recently added comment will be played first. This could be advantageous if multiple comments 322, 324 have been added to the audio image file 300 and the recipient is only interested in hearing the most recently added comments 322, 324. Alternatively, the audio commentaries 322, 324 could be added to the audio image file 300 in standard chronological order so that the first comment recorded 324 will start the audio track 320. This allows a user who views the audio image file 300 with a standard video player to hear all the comments 324, 322 in the order in which they were recorded. This may be the preferred implementation, as later-recorded commentaries will likely respond to statements made in the earlier comments.

The metadata 330 that is included in the video file 300 provides information about these two audio commentaries 322, 324. Metadata 332 contains information about the first comment 322, including the name of the user who recorded the comment (Katy Smith), the data and time at which Ms. Smith recorded this comment, and the time slice in the audio track 320 at which this comment 322 can be found. Similarly, metadata 334 provides the user name (Bob Smith), date and time of recording, and the time slice in the audio track 320 for the second user comment 324. The metadata 330 may also contain additional data about the audio image file 300, as the audio image file 300 is itself a video file and the video codec and the audio image app 132 that created this file 300 may have stored additional information about the file 300 in metadata 330.

In the preferred embodiment, the different comments 322, 324 are included in a single audio track 320 without chapter breaks. Chapter breaks are normally used to divide video files into logical breaks, like chapters in a book. The video playback facilities in some standard mobile device operating systems are not capable of displaying and managing chapter breaks, and similarly are not able to separately play different audio tracks in a video file, As a result, the audio image file 300 shown in FIG. 300 does not use separate chapters or separate audio tracks to differentiate between different user comments 322, 324. Rather, the metadata 330 is solely responsible for identifying the different comments 322, 324 in the audio track 320 of the file 300. In FIG. 3, this is done through the “time slice” data, which indicates the start and stop time (or start time and duration) of each comment in the track 320. In other embodiments, true video file chapter breaks (or even multiple tracks) could be used to differentiate between different audio comments 322, 324.

FIG. 4 shows a new audio image file 400 that is created after a third comment 422 is added to the file 300 shown in FIG. 3. As was the case with file 300, this file 400 includes a video track 410, an audio track 420, and metadata 430. The audio track 420 includes a third comment 422 in addition to the two comments 322, 324 that were found in file 300. In FIG. 4, this new comment 422 appears at the beginning of the audio track 420, as this comment 422 is the most recent comment in this audio image file 400. Similarly, the metadata 430 includes metadata 432 concerning this new track 422, in addition to the metadata 332, 334 for the prior two tracks 322, 324, respectively. Note that the time slice location of the prior two tracks 322, 324 has changed in the new audio track 420. While track 322 originally appeared at the beginning of track 320, it now appears in track 420 after the whole of track 422. Consequently, the new location of audio comments 322, 324 must now be reflected in revised versions of metadata 332, 334, respectively. In the alternative embodiment where the commentaries are recorded in the audio track 420 in chronological order, the new commentary 422 would appear after commentary 324 and commentary 322 in the audio track 420. Furthermore, in this embodiment it would not be necessary to modify metadata 332 and 334 as the time locations for these commentaries 322, 324 in track 420 would not have changed with the addition of the new commentary 422. With both embodiments, the video track 410 will again include an unchanging still image 412, much like the video track 310 of file 300. The one difference is that this video track 410 must extend for the duration of all three comments 322, 324, and 422 in the audio track 420.

User Interfaces 510, 610

FIG. 5 shows a mobile device 500 that has a touch screen display 502 and a user input button 504 located below the display 502. In this Figure, the device 500 is presenting a user interface 510 created by the audio image app 132. This interface 510 shows a plurality of audio images 520-550 that have been received by the app 132 from the server 160. The audio images 520-550 are presented in a list form, with each item in the list showing a thumbnail graphic from the audio image and the name of the individual who made the last comment on the audio image 520-550. The list in interface 510 also shows the date and time of the last comment added to each audio image. In FIG. 5, the first two audio images 520, 530 are emphasized (such as by using a larger and bold type font) to indicate to the user that these audio images 520, 530 have not yet been viewed. The interface 510 may also include an edit button 512 that allows the user to select audio images 520-550 for deletion.

In FIG. 5, the audio images 520-550 are presented in a queue in reverse chronological order, with the most recently received audio image 520 being presented at the top. In other embodiments, the audio images 520-550 are presented in a hierarchical in-box. At the top of the hierarchy are senders—the parties on the other side of a conversation with the user. After selection of a sender, the in-box presents those audio images that contain audio comments by the sender as the next level in the hierarchy. These audio images are preferably presented in reverse chronological order, but this could be altered to suit user preferences. After selection of an individual audio image, the in-box may then present the separate commentaries made in that audio image as the lowest level of the hierarchy. A user would then directly select a particular audio commentary for viewing in the app. Alternatively, the app could present the latest audio commentary to the user after the user selected a particular audio image without presenting the separate commentaries for individual selection.

If a user selects the first audio image 520 from interface 510, a new interface 610 is presented to the user, as shown in FIG. 6. This interface includes a larger version of the image 620 included in the audio image file. Superimposed on this image 620 is a play button 622, which, if pressed, will play the last audio commentary that has been added to his audio image. Below the image 620 is a list of the audio commentaries 630, 640, 650 that are included with the audio image. As seen in FIG. 6, the most recent audio commentary was created by Bob Smith on Feb. 12, 2014 at 3:13 PM, and has a duration of 0 minutes and 43 seconds. If the user selects the play button 622 (or anywhere else on the image 620), this audio commentary will be played. If the user wishes to select one of the earlier audio commentaries 640, 650 for playback, they can select the smaller playback buttons 642, 652, respectively. If more audio commentaries exist for an image 620 than can be simultaneously displayed on interface 610, a scrollable list is presented to the user.

In the preferred embodiment, the user interface 610 will remove the listings 630, 640, 650 from the display 502 when an audio commentary is being played. The image 620 will expand to cover the area of the display 502 that previously contained this list. This allows the user to focus only on the image 620 when hearing the selected audio commentary. When the user has finished listening to the audio commentary, they can press and hold the record button 660 on screen 502 to record their own response. In the preferred embodiment, the user holds the button 660 down throughout the entire audio recording process. When the button 660 is released, the audio recorded is paused. The button 660 could be pressed and held again to continue recording the user's audio commentary. When the button 660 is released, the user is presented with the ability to listen to their recording, re-record their audio commentary, delete their audio commentary, or send a new audio image that includes the newly recorded audio commentary to the sender (in this case Bob Smith) or to a third party. By pressing the back button 670, the user will return to interface 510. By pressing the share button 680 without recording a new commentary, the mobile device 500 will allow a user to share the selected audio commentary 520 as it was received by the device 500.

Methods 700, 800, 900

The flowchart in FIG. 7 shows a method 700 for creating, sending, and playing an audio image file. This method 700 will be described from the point of view of the system 100 shown in FIG. 1. The method begins at step 705, when the originator of an audio image either selects an image from the existing photos 146 already on their mobile device 110, or creates a new image using camera 114. At step 710, the app 132 shows the selected image to the user and allows the user to record an audio commentary, such as by holding down a record button (similar to button 660) presented on the touch screen 116 of the mobile device 110. The app 132 will then use a video codec, such as may be provided by the mobile device operating system 140, to encode both the image and the audio commentary into a video file (step 715). The app 132 will also add metadata 330 to the video file to create an audio image file 300 at step 720. The metadata 330 provides sufficient information about the audio track 320 of the audio image file 300 to allow another device operating the app 132 to correctly play the recorded audio commentary.

Once the audio image file 300 is created, the app 132 will, at step 725, present a user interface to allow the originator to select a recipient (or multiple recipients) for this file 300. As explained above, the app 132 may present the user with their existing contact list 148 to make it easier to select a recipient. In some cases, a recipient may have multiple possible audio image addresses 260 at which they can receive the audio image file 300. For instance, a user may have two e-mail addresses 230 and two cellular telephone numbers 240. In these cases, the app 132 can either request that the originator select a single audio image address for the recipient, or the app can select a “best” address for that user. The best address can be based on a variety of criteria, including which address has previously been used to successfully send an audio image file to that recipient in the past.

Once the recipient is selected, the app 132 will determine at step 730 whether or not the recipient is a user of the app 132. As explained above, this can be accomplished by the app 132 sending a query to the audio image server 160 requesting a determination as to whether the audio image address for that recipient is associated with a known user of the app 132. If the recipient has multiple possible audio image addresses, the query may send all of these addresses to the server 160 for evaluation. If the recipient is not a known user of the app 132, this will be determined at step 735. Step 740 will then determine whether the selected or best audio image address is an e-mail address or a cell phone number. If it is an e-mail address, step 745 will create and send an e-mail 172 to the recipient. This e-mail 172 will include the audio image file 300 as an attachment to the e-mail. In addition, the e-mail will include a link to the download location 190 for the app 132 along with a message indicating that the app 132 is needed to create and send a reply to the audio image. If step 740 determines that the audio image address 260 is a cell phone number, then step 750 will create and send an MMS message 182 to the recipient. As was true of the e-mail 172, the MMS message 182 will include the audio image file as an attachment, and will include a link to download location 190 along with a message stating that the app 132 is necessary to create a reply to the audio image.

After sending an e-mail at step 745 or an MMS message at step 750, step 755 will also send the audio image file and relevant transmission information to the audio image server 160. This transmission information may include the time of the e-mail or MMS transmission, the time that the audio comment was generated, the name of the originator and the recipient, and the recipient's chosen audio image address. This information will then be stored in database 164 along with the audio image file itself (step 760). As shown in FIG. 7, these same steps 755, 760 will also occur if step 735 determined that the recipient was a user of the app 132, as the server 160 needs this information to complete the transmission to the recipient. In fact, since the server 160 always receives this information from the sending mobile device 110 regardless of the transmission type, it is possible to eliminate the separate query of step 730. In this alternative embodiment, the transmission of the information at step 755 would occur at step 730. The app 132 would be informed if the recipient were not a user of the app 132, allowing steps 740-750 to proceed. If the app 132 on mobile device 110 instead received notification that the server 160 was able to transmit the information directly to the recipient, then no additional actions would be required on behalf of the sending mobile device 110.

Once the server 160 has received the transmission information at step 755 and stored this information in database 164 at step 760, step 765 considers whether the recipient is a user of the app 132. If not, the server 160 need not take any further action, as the sending mobile device 110 is responsible for sending the audio image file to the recipient. In this case, the method 700 will then end at step 790 (method 900 shown in FIG. 9 describes the receipt of an audio image file by a mobile device that does not use the app). In the alternative embodiment where step 730 is removed, the server 160 would at this time inform the transmitting mobile device 110 that the recipient is not a user of the app 132.

Assuming that the recipient is using the app 132, then the server 160 transmits the audio image file 300 to the recipient mobile device 168. The recipient device 168 receives the audio image file 300 at step 770, and then provides a notification to the user than the file 300 was received. The notification is preferably provided using the notification features built into the operating systems of most mobile devices 168. At step 775, the app 132 is launched and the user requests the app 132 to present the audio image file 300. At step 780, the image is then displayed on the screen and this audio commentary is played. At this time, the user may request to record a reply message. If step 785 determines that the user did not desire to record a reply, the method 700 ends at step 790. If a reply message is desired, then method 800 is performed.

Method 800 is presented in the flow chart found in FIG. 8. The method starts at step 805 with the user of mobile device 168 indicating that they wish to record a reply. In the embodiments described above, this is accomplished by holding down a record button 660 during or after viewing the video image file 300. When the user lets go of the record button 660, the audio recording stops. At step 810, the audio recording is added to the beginning of the audio track 320 of the audio image file 300. With some codecs, the combining of two or more audio commentaries into a single audio track 320 can be accomplished by simply merging the two files without the need to re-compress the relevant audio. Other codecs may require other techniques, which are known to those who are of skill in the art. At step 815, the video track 310 is extended to cover the duration of all of the audio commentaries in the audio track 320. Finally, at step 820 metadata is added to the new audio image file. This metadata will name the reply commentator, and will include information about the time and duration of the new comment. This metadata must also reflect the new locations in the audio track for all pre-existing audio comments, as these comments will now appear later in the new audio image file.

At step 825, mobile device 168 sends the new audio image file to the server 160 for transmission to the originating device 110. Note that the transmission of a reply to the originating device 110 may be assumed by the app 132, but in most cases this assumption can be overcome by user input. For instance, the recipient using mobile device 168 may wish to record a commentary and then send the new audio image file to a mutual friend, or to both the originator and mutual friend. In this case, the workflow would transition to step 730 described above. For the purpose of describing method 800, it will be assumed that only a reply to the originating device 110 is desired.

The server will then store the new audio image file and the transmission information in its database 164 (step 830), and then transmit this new file to the originating mobile device 110 (step 835). App 132 will then notify the user through the touch screen interface 116 that a new audio image has been received at step 840. When the app 132 is opened, the app 132 might present all of the user's audio image files in a list, such as that described in connection with FIG. 5 (step 845). If the user request that the app 132 play the revised audio image file, the app 132 will display the original image and then play back the reply audio message at step 850. The metadata 330 in the file 300 will indicate when the reply message ends, allowing the app 132 to stop playback before that portion of the video file containing the original message is reached. As indicated at step 855, the app 132 can also present to the user a complete list of audio comments that are found in this audio image file 300, such as through interface 610 shown in FIG. 6.

In some cases, an audio image file may contain numerous comments. To assist with the management of comments, the app 132 can be designed to allow a user to filter the audio comments so that not all comments are displayed and presented on interface 610. For instance, a user may wish to only know about comments made by friends that are found in their contact records 148 or are made by the individual who sent the message to the user. In this instance, interface 610 would display only the comments that the user desired. The interface 610 may also provide a technique for the user to reveal the hidden comments. The user is allowed to select any of the displayed comments in the list for playback. The app 132 would then use the metadata 330 associated with that comment to play back only the relevant portion of the audio track 320 (step 860). The originator would also have the ability to create their own reply message at step 865. If such a re-reply is desired, the method 800 would start again. If not, the method 800 ends at step 870.

FIG. 9 displays a flow chart describing the method 900 by which a non-user of the app 132 is able to download the app 132 and see previously transmitted messages. The method 900 begins at step 905 when the user receives an e-mail or an MMS message containing an audio image file 300. When the e-mail or MMS message is opened, it will display a message indicating that the app 132 is required to create a reply (step 910). The message will also include a link to the app 132 at an app store 190, making the download of the app 132 as simple as possible.

Since the audio image file 300 that is sent in this context is a video file, the user can play the audio image file as a standard video file at step 915. This would allow the user to view the image and hear the audio commentaries made about the image. If more than one audio commentary were included in the audio image file 300, a standard video player would play through all of the commentaries without stopping. Whether the commentaries would play in chronological order or in reverse chronological order will depend completely on the order in which the commentaries were positioned in the audio track, as described above in connection with FIGS. 3 and 4. When a standard video player is used to play the audio image file 300, the user will not be able to add a new audio commentary to this file 300.

If the user wishes to create a new comment, they will select the provided link to app store 190. This selection will trigger the downloading of the app 132 at step 920. When the user initiates the app 132 by selecting the app's icon in the app selection screen of the operating system at step 925, the app 132 will request that the user enter personal information into the app. In particular, the app 132 will request that the user provide their name, their e-mail address(es), and their cell phone number(s). This information is received by the app 132 at step 930, and then transmitted to the server 160. The server 160 will then create a new user record 220 in the database 164, give that record 220 a new User ID 250, and then associate that user record 220 with the user provided e-mail addresses 230 and cell phone numbers 240 (step 935).

At step 940, the server 160 will search the database for audio image messages 200 that have been previously sent to one of the e-mail addresses 230 or cell phone numbers 240 associated with the new user record 220. All messages 200 so identified will be downloaded, along with the actual audio image file or data 210, to the user's app 132 at step 945. The user can then view the downloaded audio image files (such as through user interface 510 of FIG. 5), select one of the audio image files (as shown in FIG. 6), and then view the audio image file 300 through the app 132 (step 950). Step 950 will also allow the user to create reply audio messages through method 800, and transmit the resulting new audio image files to other users. The process 900 then terminates at step 955.

Deletion of Audio Image Files

As described above, the database 164 is designed to receive a copy of all audio image data files 300 that are transmitted using system 100. In addition, app 132 may store a copy of all audio image data files 300 that are transmitted or received at a mobile device 110. In the preferred embodiment, the app 132 is able to selectively delete local copies of the audio image data files 300, such as by using edit button 512 described above. To the extent that the same data is stored as database entity 210 in the database 164 managed by server 160, it is possible to allow an app 132 to undelete an audio image file 300 by simply re-downloading the file from the server 160. If this were allowed, the server would require the user re-authenticate themselves, such as by providing a password, before allowing a download of a previously deleted audio image file.

In some embodiments, the server 160 will retain a copy of the audio image file 300 as data entity 210 only as long as necessary to ensure delivery of the audio image. If all recipients of an audio image file 300 were users of the app 132 and had successfully downloaded the audio image file 300, this embodiment would then delete the audio image data 210 from the database 164. Meta information about the audio image could still be maintained in database entity 200. This would allow the manager of server 160 to maintain information about all transmissions using system 100 while ensuring users that the actual messages are deleted after the transmission is complete. If some or all of the recipients are not users of the app 132, the server 160 will keep the audio image data 210 to allow later downloads when the recipients do become users of the app 132. The storage of these audio image files in database 164 can be time limited. For example, one embodiment may require deletion of all audio image data 210 within three months after the original transmission of the audio image file even if the recipient has not become a user of the app 132.

The many features and advantages of the invention are apparent from the above description. Numerous modifications and variations will readily occur to those skilled in the art. For example, the above description indicated that the audio image files 300 received by the app 132 are formatted as video files. While standard video files will be sent as e-mail and MMS attachments to users that do not utilize the app 132, the app 132 could receive an audio image file in a proprietary format and still be within the scope of the present invention. Since such modifications are possible, the invention is not to be limited to the exact construction and operation illustrated and described. Rather, the present invention should be limited only by the following claims. 

What is claimed is:
 1. A computerized method comprising: a) at a first mobile device, receiving a remote audio image file from a remote mobile device, the remote audio image file having i) a video portion, and ii) an audio portion having a remote commentary added to the remote audio image file by the remote mobile device; b) presenting the video portion of the remote audio image file through a display screen of the first mobile device; c) while presenting the video portion, presenting the remote commentary in the audio portion of the remote audio image file over an audio output of the first mobile device; d) after presenting the remote commentary, recording a new commentary through a microphone input of the first mobile device; e) at the first mobile device, creating a new audio image file by adding the new commentary to the remote commentary in the audio portion of the remote audio image file; and f) transmitting the new audio image file to the remote mobile device.
 2. The method of claim 1, wherein the remote audio image file further has: iii) metadata indicating a remote creator name and a remote creation time for the remote commentary;
 3. The method of claim 2, wherein the step of creating the new audio image file further comprised adding to the metadata of the remote audio image file an indication of a new commentary creator name and a new commentary creation time for the new commentary.
 4. The method of claim 3, wherein the audio portion of the new audio image file is a single track without chapter breaks, and further wherein the metadata identifies a location within the single track and a duration for each commentary in the audio portion.
 5. The method of claim 2, wherein the remote audio image file contains a plurality of commentaries and the metadata indicates a creator name, creation time, time location, and time duration for each of the plurality of commentaries.
 6. The method of claim 5, wherein the plurality of commentaries are arranged in the audio portion in reverse chronological order.
 7. The method of claim 5, wherein the remote audio image file is video file recorded using a video codec, further wherein the steps of presenting the video portion and the step of presenting the remote commentary comprises playing the video file from the time location and for the time duration indicated in the metadata for the remote commentary.
 8. The method of claim 5, wherein the video portion consists of a single fixed image.
 9. The method of claim 1, wherein the step of creating the new audio image file further comprises extending a duration of the video portion of the remote audio image file to compensate for a duration of the new commentary.
 10. A computerized method comprising: a) at a mobile device, selecting a photographic image; b) at the mobile device, recording an audio commentary; c) at the mobile device, encoding the photographic image and the audio commentary into a video file showing the photographic image along with the audio commentary; d) at the mobile device, receiving a selection of a recipient to receive the video file; e) at the mobile device, receiving an indication from the remote server that a first contact is a user of a compliant app; f) at the mobile device, sending the video file to the first contact via the remote server, wherein the remote server forwards the video file to the compliant app on a first contact mobile device associated with the first contact.
 11. The computerized method of claim 10, further comprising: g) at the mobile device, receiving an indication from the remote server that a second contact is not using of the compliant app; and h) at the mobile device, sending the video file to the second contact via an MMS message to a second contact mobile device associated with the second contact.
 12. The computerized method of claim 11, wherein the MMS message includes a link to a download location for the compliant app.
 13. The computerized method of claim 11, further comprising: i) at the mobile device, receiving an indication from the remote server that a third contact is not using of the compliant app; and j) at the mobile device, sending the video file to the second contact via an e-mail message to a third contact mobile device associated with the third contact.
 14. The computerized method of claim 11, wherein the plurality of contacts comprise a plurality of e-mail address and telephone numbers, further wherein the request to the remote server transmits the plurality of e-mail addresses and telephone numbers.
 15. A computerized method comprising: a) receiving, at a server computer, a communication that a video file was transmitted from a first mobile device to an electronic delivery address; b) storing, at the server computer, the video file and the electronic delivery address in a database; c) receiving, at the server computer and from a second mobile device, a new user registration for an app operating on the second mobile device, the new user registration including the electronic delivery address as a contact address; d) locating, at the server computer, the video file in the database associated with the electronic delivery address; and e) transmitting, from the server computer and to the app on the second mobile device, the video file.
 16. The computerized method of claim 15, wherein the electronic delivery address is of a type selected from a set comprising an e-mail address and a telephone number. 